Synced 02 Nov 2026 13:39 UTC Account

Is JBoss 4.3.0 CP10 patched?

Red Hat · cycle 4.3 · end of life
4.3.0 CP1040/100End of life

Current stable (8.1.9): 97/100

Minimum safe version7.2.4

4.3.0 CP10 has 3 open critical-or-high vulnerabilities. Run 7.2.4 or later to clear them. See what 7.2.4 fixes →

Upgrade impact: Major upgrade (3 major versions). Crossing a major version usually means breaking changes. Review the vendor’s upgrade / migration guide and test before you roll it out.

Health score40/100
Open issues24
Exploited now0
Cycle 4.3 EOL2013-01-31
Latest release8.1.9

Summary iPlain-English security status for JBoss 4.3.0 CP10, built from its CVEs, active-exploitation data, end-of-life date and latest release.

JBoss 4.3.0 CP10 is part of the 4.3 release line. 24 known vulnerabilities affect it. The minimum safe version is 7.2.4 — upgrade to it or later to clear the open critical/high issues. The 4.3 line reached end-of-life on 2013-01-31, so it no longer receives security patches. The latest supported JBoss release is 8.1.9.

Other JBoss versions

Check another release line of JBoss.

Frequently asked

Is JBoss 4.3.0 CP10 patched?

JBoss 4.3.0 CP10 is end-of-life and no longer receives security patches. Move to 8.1.9.

What version should I upgrade JBoss 4.3.0 CP10 to?

Upgrade JBoss 4.3.0 CP10 to at least 7.2.4 to clear its 3 open critical-or-high vulnerabilities.

When does JBoss 4.3 reach end-of-life?

JBoss 4.3 reached end-of-life on 2013-01-31 and no longer receives security patches.

What is the latest version of JBoss?

The latest supported JBoss release is 8.1.9.

Is JBoss 4.3.0 CP10 still receiving security updates?

No — JBoss 4.3.0 CP10 is on the 4.3 line, which reached end-of-life on 2013-01-31 and no longer receives security updates. Upgrade to 8.1.9 or later to stay supported.

Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Red Hat's official advisory before you patch or upgrade.